The Portuguese Camino is one of the most popular routes of the Camino de Santiago, known for its history, natural beauty, and rich cultural heritage. Within this journey, the Spiritual Variant offers a unique option for pilgrims seeking a deeper and more special experience, blending history, nature, and spirituality.
In this article, we’ll explore the differences between the Spiritual Variant and the traditional Portuguese Camino, helping you decide which path best suits your preferences.
Traditional Portuguese Camino: History and Cultural Wealth
The Traditional Portuguese Camino is characterized by connecting historical cities and rural landscapes, offering a journey that passes through iconic places like Porto, Ponte de Lima, and Tui. It is a well-traveled route thanks to its accessibility, well-developed infrastructure, and the opportunity to discover the cultural richness of Portugal and Galicia.
Key Features of the Traditional Portuguese Camino:
Total distance: Approximately 620 kilometers from Lisbon or 240 kilometers from Porto.
Route: Predominantly land-based, crossing rural paths, forests, and historical towns.
Highlights: Porto Cathedral, the medieval town of Ponte de Lima, Tui, and the town of Padrón, famous for its peppers and its connection to the Apostle Santiago legend.
The Traditional Portuguese Camino is ideal for those looking for a more classic Camino de Santiago experience, with a mix of nature and culture.
Spiritual Variant: A Unique and Different Route
The Spiritual Variant of the Portuguese Camino is an alternative to the traditional land-based route, adding a maritime and spiritual dimension to the journey. This variant connects Pontevedra to Vilanova de Arousa, passing through iconic landmarks like the Monastery of Armenteira and the “Ruta da Pedra e da Auga,” culminating in the Traslatio Route, the only maritime stage of the Camino de Santiago.
Key Features of the Spiritual Variant:
Total distance: Approximately 73 kilometers, divided into three stages.
Mixed route: Combines hiking through natural landscapes with a boat journey along the Ría de Arousa and the Ulla River.
Highlights: The Monastery of Poio, the Ruta da Pedra e da Auga, the Monastery of Armenteira, and the world’s only maritime-fluvial Via Crucis.
Main Differences Between Both Options
Aspect
Traditional Portuguese Camino
Spiritual Variant
Route
Mainly land-based
Combination of hiking and maritime stage
Distance
From Porto: 240 km
73 km from Pontevedra
Highlights
Historic cities and rural landscapes
Monasteries, Ruta da Pedra e da Auga, and Ría de Arousa
Difficulty
Moderate
Moderate, with some steep sections
Unique Experience
Connection with history and culture
Spiritual and maritime dimension
Which One to Choose?
The choice between the Traditional Portuguese Camino and the Spiritual Variant depends on what you seek as a pilgrim. If you prefer a more conventional and linear route, the traditional path is for you. However, if you’re looking for something different, with a deeper connection to nature and the history of the Apostle Santiago, the Spiritual Variant is your best choice.
Discover the Traslatio Route with Barco Variante Espiritual
The Traslatio Route, part of the Spiritual Variant, is the only maritime stage of the Camino de Santiago and an experience you cannot miss. Book your spot and enjoy a journey that combines history, spirituality, and nature in the Ría de Arousa.
We thank you for contacting us and we assure you that we will do everything possible to accommodate your request.
If you continue this conversation, you have given us your consent to contact you in this way. We take this opportunity to inform you that we will use the data generated in this conversation to assist you and provide you with our services.
You can exercise your rights at the email address info@amareturismonautico.com. More information in our offices and on our website.
Privacy Overview
This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.
Analytics Cookies
This website uses Google Analytics to collect anonymous information such as the number of visitors to the site, or the most popular pages.
Leaving this cookie active allows us to improve our website.
Please enable Strictly Necessary Cookies first so that we can save your preferences!
Show details
Name
Provider
Purpose
Expiration
_ga
Google Analytics
Esta cookie es instalada por Google Analytics. La cookie se utiliza para calcular los datos de visitantes, sesiones, campañas y realizar un seguimiento del uso del sitio para el informe de análisis del sitio. Las cookies almacenan información de forma anónima y asignan un número generado aleatorio para identificar visitantes únicos.
1 año
_gat
Google Analytics
Forma parte de Google Analytics. Se usa para limitar el porcentaje de solicitudes.
1 año
_gid
Google Analytics
Forma parte de Google Analytics. Se usa para distinguir a los usuarios.
24 horas
_hjClosedSurveyInvites
Hotjar
Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.
365 days
_hjDonePolls
Hotjar
Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.
365 days
_hjMinimizedPolls
Hotjar
Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.
365 days
_hjShownFeedbackMessage
Hotjar
Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.
365 days
_hjSessionTooLarge
Hotjar
Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
Session
_hjSessionRejected
Hotjar
If present, this cookie will be set to '1' for the duration of a user's session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.
Session
_hjSessionResumed
Hotjar
Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
365 days
_hjRecordingLastActivity
Hotjar
This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
Session
_hjTLDTest
Hotjar
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
Session
_hjUserAttributesHash
Hotjar
User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
Session
_hjCachedUserAttributes
Hotjar
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar Feedback tool, but the cookie will be used regardless of whether a Feedback tool is present.
Session
_hjLocalStorageTest
Hotjar
This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
Under 100ms
_hjIncludedInPageviewSample
Hotjar
This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
30 minutes
_hjIncludedInSessionSample
Hotjar
This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.
30 minutes
_hjAbsoluteSessionInProgress
Hotjar
This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
Session
_hjViewportId
Hotjar
This stores information about the user viewport such as size and dimensions.
Session
_hjRecordingEnabled
Hotjar
This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.
Session
Additional cookies
This website uses the following additional cookies:
(List here the cookies you are using on the website.)
Please enable Strictly Necessary Cookies first so that we can save your preferences!
Show details
Name
Provider
Purpose
Expiration
_fbp
Facebook
Cookie de Facebook utilizadas para recoger estadísticas sobre las visitas al sitio y el rendimiento de las campañas publicitarias